Skip to content

Conversation

michaellee1019
Copy link
Member

@michaellee1019 michaellee1019 commented Oct 8, 2025

Changes how reload versions are stored and incorporates @gmulz's idea of making hot reloading storage at the part level to avoid issues if two developers hot reload the same module on different parts:

  1. The source code is stored as "reload-source-" version within the module's packages. Instead of a general "reload" source module.
  2. The built artifacts is stored in a similar "reload-" version.

Testing

Did full round of testing to ensure the workflow passed in a preview environment along with app changes. Verified in our DB that it contained both versions while after the build finished, and then once the copy to part finished, that the source code was deleted.

@viambot viambot added the safe to test This pull request is marked safe to test from a trusted zone label Oct 8, 2025
@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Oct 8, 2025
@michaellee1019 michaellee1019 marked this pull request as ready for review October 8, 2025 21:58
Copy link
Member

@gmulz gmulz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

didn't get a chance to test this on my own, but i trust your testing and the code changes seem reasonable

const reloadVersion = "reload"
const (
reloadVersionPrefix = "reload"
reloadSourceVersionPrefix = "reload-source"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the difference between these two? one is the source tarball that gets fed into cloud build, the other is the binary artifact that is produced?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup that is the difference.

Copy link
Member

@stuqdog stuqdog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

didn't test but looks good to me!

@michaellee1019
Copy link
Member Author

michaellee1019 commented Oct 14, 2025

didn't test but looks good to me!

I did a lot of testing myself so I'm confident in this change.

@Ethan I think lets do some testing together later in the week. Or I can handle it. After both our changes are merged in. And probably with the reload progress spinner changes if I have that merged in time.

This way we can make sure everything in main across all projects works together.

@viambot viambot added safe to test This pull request is marked safe to test from a trusted zone and removed safe to test This pull request is marked safe to test from a trusted zone labels Oct 14, 2025
@michaellee1019 michaellee1019 merged commit b9e3230 into viamrobotics:main Oct 14, 2025
18 checks passed
@michaellee1019 michaellee1019 deleted the ml/reload-version-partitioning branch October 14, 2025 23:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to test This pull request is marked safe to test from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants